Skip to content

scylla 2022 upgrade, monitoring 4.0, manager 3.0#153

Open
tarzanek wants to merge 1 commit intoscylladb:masterfrom
tarzanek:2022-upgrade
Open

scylla 2022 upgrade, monitoring 4.0, manager 3.0#153
tarzanek wants to merge 1 commit intoscylladb:masterfrom
tarzanek:2022-upgrade

Conversation

@tarzanek
Copy link
Collaborator

No description provided.

Copy link
Collaborator

@vladzcloudius vladzcloudius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, put a little more detailed description for the patch.
In particular, describe the motivation for it.

@tarzanek
Copy link
Collaborator Author

tarzanek commented Sep 23, 2022

will fix the message
anyhow the bigger problem is the failing test

because molecule stopped working for newer Scylla versions, so we diverged somewhere and there are no logs,
seems we need a way to make molecule show more logs about service failure

 TASK [ansible-scylla-node : start scylla on node2] *****************************
  fatal: [node2]: FAILED! => {"changed": false, "msg": "Unable to start service scylla-server: Job for scylla-server.service failed because a fatal signal was delivered causing the control process to dump core.\nSee \"systemctl status scylla-server.service\" and \"journalctl -xe\" for details.\n"}

so something signaled the service to die, but we don't know what

@tarzanek
Copy link
Collaborator Author

once #232 is merged, this can be updated
molecule deployment fixed as per Dimas changes and merged too (reminder for myself)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants